Scheduling Extract Refreshes in Tableau

Topic: Scheduling, Automating, Monitoring, and Troubleshooting Extract Refreshes in Tableau Server and Tableau Cloud.

Course Link: Explore Tableau Training

Demo Link: Register for a Tableau Course Demo

1. Introduction to Scheduling Extract Refreshes

Tableau is a business intelligence and data visualization platform used to create interactive dashboards, reports, charts, and data-driven insights. Tableau can connect to databases, spreadsheets, cloud applications, and other data sources. When a workbook uses an extract, Tableau works with a saved snapshot of the source data rather than querying the original source for every interaction.

Scheduling Extract Refreshes means configuring Tableau to update an extract automatically at specific times or intervals. This allows dashboards and reports to reflect newly available source data without requiring someone to refresh the extract manually each time.

For example, a sales department may have a dashboard that displays yesterday's sales figures. If the extract refreshes every morning at 6:00 AM, the dashboard can show the latest available information after the refresh completes successfully.

Why Is Extract Refresh Scheduling Important?

• Automates data updates and reduces manual work.
• Helps dashboards display recent information.
• Supports regular reporting for business departments.
• Improves the reliability of recurring reports.
• Allows refreshes to run during quieter periods.
• Helps manage large data sources and server resources.
• Supports consistent data availability for business decisions.

Important: A scheduled refresh does not guarantee that a dashboard always contains real-time data. The freshness of the dashboard depends on the schedule, source-data availability, refresh duration, connection configuration, and whether the refresh succeeds.

2. What Is a Tableau Data Extract?

A Tableau data extract is a stored snapshot or subset of data created from an original data source. Tableau extracts commonly use the Hyper data engine format and can improve performance for many analytical workloads.

Instead of repeatedly querying the original database for every interaction, Tableau can query the extracted data. The extract must be refreshed when new or changed source data needs to appear in the extract.

Example

A company maintains a database containing five years of sales transactions. A Tableau developer creates an extract containing the relevant sales fields and publishes a dashboard to Tableau Cloud or Tableau Server.

When new sales transactions are added to the original database, the published extract does not automatically include them simply because the source database changed. A successful refresh is needed to update the extract.

Advantages of Extracts

• Can improve dashboard responsiveness.
• Can reduce repeated queries against the original database.
• Can support analysis when the original source is temporarily unavailable, using the data already stored in the extract.
• Can contain a filtered or reduced dataset for specific analytical requirements.
• Can support scheduled and incremental updates.

Limitations of Extracts

• The data can become outdated between refreshes.
• Refreshing large extracts can consume time and computing resources.
• Credentials or connectivity problems can cause refresh failures.
• Extracts require storage and maintenance.
• Full refreshes may be expensive when the source contains a large volume of data.

3. What Is an Extract Refresh?

An extract refresh is the process of updating a Tableau extract using data from its original source. It may replace the existing extracted data or update it incrementally, depending on how the extract is configured.

Example

Consider an e-commerce company with a sales database. At the end of each business day, new orders are inserted into the database. A scheduled refresh can update the published extract so that the sales dashboard includes those orders.

Original Database
       |
       v
Tableau Extract
       |
       v
Scheduled Refresh
       |
       v
Updated Extract
       |
       v
Tableau Dashboard
       |
       v
Updated Business Insights

When the refresh succeeds, the extract contains the data retrieved according to the configured refresh type and connection settings. If a refresh fails, the extract may remain at its previous successful state, so users should check the job status rather than assume the data was updated.

4. Types of Extract Refreshes

Tableau commonly supports two principal refresh approaches: full refresh and incremental refresh. Availability and configuration depend on the data source and publishing environment.

4.1 Full Refresh

A full refresh reloads the extract from the source according to the extract's definition. It is useful when the extract must be rebuilt to reflect source changes, including changes that an incremental refresh would not capture.

Example: A retail company refreshes its product and sales extract every Sunday to rebuild the extracted data from the source.

Advantages:

• Rebuilds the extract using the current source data.
• Can capture source changes that are not covered by an incremental strategy.
• Is useful when data is frequently updated or corrected throughout its history.

Disadvantages:

• May take longer for large datasets.
• May consume more database, network, and server resources.
• Can be less efficient when only a small number of new records are added.

4.2 Incremental Refresh

An incremental refresh adds new records identified using a configured field or updates the extract according to the supported incremental-refresh behavior. The extract must be configured for incremental refresh before the applicable published refresh task can use that option.

Incremental refresh is particularly useful when a source table mainly receives new records and historical records do not need to be rebuilt on every refresh.

Example: A transaction table receives thousands of new sales records every day. Tableau can use a suitable transaction ID or date field to identify records for incremental processing, provided the field and source support the configured strategy.

Advantages:

• Can reduce refresh time for suitable datasets.
• Can reduce repeated processing of historical data.
• Can make frequent updates more practical for large transaction tables.

Limitations:

• Must be configured appropriately before publishing.
• May not capture changes to existing historical records as expected.
• Deletes, corrections, and late-arriving data require special consideration.
• Depends on the chosen incremental field and the source's data behavior.

4.3 Full Refresh vs Incremental Refresh

Best practice: Use incremental refresh when it reliably captures the changes your business needs. Schedule full refreshes when necessary to account for historical corrections, deleted records, or changes that the incremental strategy cannot capture.

5. Tableau Server vs Tableau Cloud Refresh Scheduling

The process for scheduling an extract refresh depends on where the content is published and where the original data is hosted.

Tableau Cloud cannot directly reach every private network or data source. Tableau Bridge extends connectivity for supported private-network data sources and is often required for on-premises data. Always check the source-specific refresh requirements.

Official guide: Schedule Extract Refreshes as You Publish a Workbook

Official guide: Schedule Refreshes on Tableau Cloud

6. Prerequisites for Scheduling Extract Refreshes

Before creating a schedule, confirm that the extract and its published content are configured correctly.

• Published content: The workbook or data source containing the extract is published to the intended Tableau site.
• Refresh capability: The user has the permissions required to create or manage the refresh task.
• Source connectivity: Tableau Server or Tableau Cloud, directly or through Bridge, can reach the source.
• Authentication: Credentials, OAuth authorization, or other supported authentication are configured for unattended refreshes.
• Extract configuration: The workbook or data source actually uses an extract rather than relying only on a live connection.
• Schedule availability: The deployment supports the required schedule and has sufficient task capacity.
• Source stability: The database, file, or application is available at the scheduled time.
• Data permissions: The account used for refresh has the required source-data access.
• Refresh strategy: Full or incremental refresh is selected according to the data requirements.

On Tableau Server, administrators and authorized content owners can manage appropriate refresh tasks. Exact privileges vary with ownership, site role, project leadership, and site configuration.

7. How to Schedule an Extract Refresh in Tableau Server

This procedure describes the general workflow for a published extract on Tableau Server. Menu names can vary by version and deployment.

Step 1: Publish the Workbook or Data Source

1. Open Tableau Desktop.
2. Connect to the required database, spreadsheet, or other supported source.
3. Prepare the required fields, filters, calculations, and worksheets.
4. Choose an extract connection where appropriate.
5. Select Server > Publish Workbook or the relevant data-source publishing command.
6. Sign in to the correct Tableau Server site.
7. Choose the project where the content should be published.
8. Review the extract and authentication options.
9. Publish the content.

Step 2: Open the Refresh Scheduling Options

1. During publishing, locate the Schedules & Authentication section when it is available.
2. Select an appropriate extract refresh schedule.
3. Configure the required authentication for accessing the original source.
4. Review whether a full or incremental refresh is appropriate and supported.
5. Finish publishing the workbook or data source.

Step 3: Configure or Review the Schedule

1. Sign in to Tableau Server with an authorized account.
2. Open the Schedules or relevant task-management area.
3. Review available refresh schedules or create a new schedule if permitted.
4. Set the required frequency and time.
5. Configure other supported schedule options, such as priority, if necessary.
6. Associate the correct refresh task with the schedule.
7. Save the configuration.

Step 4: Test the Refresh

1. Locate the published workbook or data source.
2. Run the refresh on demand if the action is available to you.
3. Wait for the job to finish.
4. Check the job status and any error details.
5. Open the dashboard and verify that the expected data appears.

Tip: Scheduling and publishing settings depend on your permissions. If the scheduling option is missing, confirm the user's privileges, the connection type, and the server's schedule configuration.

Official guide: Quick Start to Refresh Extracts on a Schedule

8. How to Schedule an Extract Refresh in Tableau Cloud

Tableau Cloud can schedule refreshes for supported cloud-hosted sources. Private-network data and some other connections may require Tableau Bridge.

Step 1: Open the Published Content

1. Sign in to Tableau Cloud.
2. Select Explore from the navigation pane.
3. Open All Workbooks or All Data Sources, depending on the content you want to refresh.
4. Find the workbook or data source that contains the extract.

Step 2: Open Extract Refresh Actions

1. Select the checkbox for the required workbook or data source.
2. Open Actions.
3. Select Refresh Extracts.
4. In the refresh dialog, select the option to schedule a refresh when available.

Step 3: Configure Refresh Settings

• Refresh Type: Select Full Refresh or Incremental Refresh when the configuration supports it.
• Refresh Frequency: Choose an appropriate hourly, daily, weekly, or monthly schedule when offered.
• Time: Select a time that matches business requirements and the site's scheduling options.
• Day or Interval: Configure the applicable days or recurrence details.

Step 4: Save and Validate

1. Save the schedule.
2. Check the published content's refresh settings.
3. Run a test refresh if the action is available.
4. Confirm that the refresh completes successfully.
5. Check the dashboard to verify the updated data.

Note: Tableau Cloud's scheduling interface and supported options can change. If the source requires Tableau Bridge, configure Bridge and its connection before expecting scheduled refreshes to work.

9. Understanding Refresh Frequency

Refresh frequency determines how often Tableau attempts to update an extract. The best frequency depends on how often the source data changes, how quickly users need the information, and the resources required to process the refresh.

The exact schedule options depend on the Tableau environment and the configured scheduling interface.

How to Choose the Right Frequency

• Use hourly refreshes when business decisions depend on frequent updates and the source can support them.
• Use daily refreshes for reports that are reviewed once per business day.
• Use weekly refreshes when the source data changes infrequently.
• Use monthly refreshes for data that only needs periodic updates.
• Avoid refreshing too frequently if the source data does not change often.
• Schedule expensive tasks outside peak database usage when possible.

10. Full Refresh vs Incremental Refresh in a Scheduled Job

Choosing a refresh type is an important part of designing a reliable schedule. The schedule defines when a refresh runs, while the refresh type defines how Tableau updates the extract.

Example: Daily Sales Report

A sales database receives new transactions every day. A possible design is to configure an incremental refresh for frequent updates and perform a full refresh at an appropriate interval if historical changes need to be reconciled.

Daily at 6:00 AM
       |
       v
Incremental Refresh
       |
       v
New qualifying records are processed
       |
       v
Dashboard is checked

Periodic reconciliation
       |
       v
Full Refresh when needed
       |
       v
Historical data is rebuilt

This is an example strategy, not a universal requirement. Some sources need a full refresh each time, while others work well with incremental refreshes. Validate the strategy against the source's update patterns.

When Should You Use a Full Refresh?

• Historical rows can change or be deleted.
• The incremental field does not capture all changes.
• The extract definition or data structure requires a rebuild.
• A full rebuild is needed to validate data completeness.

When Should You Use an Incremental Refresh?

• New records are regularly appended to the source.
• A suitable incremental field is available.
• The data source and extract support incremental refresh.
• Refresh time or resource usage needs to be reduced.

11. Scheduling Extracts with Tableau Bridge

Tableau Bridge is a client application that helps Tableau Cloud access supported data sources that are not directly reachable from the cloud, such as databases and files inside a private network.

When Is Tableau Bridge Required?

• The data source is on a private or on-premises network.
• Tableau Cloud cannot directly establish the required connection.
• The connection type and refresh method are supported by Bridge.

General Bridge Setup Process

1. Install Tableau Bridge on a supported computer or server with network access to the source.
2. Sign in to the appropriate Tableau Cloud site.
3. Configure Bridge according to the organization's network and security requirements.
4. Confirm that Bridge can connect to the underlying database or file.
5. Configure the published data source or workbook to use the appropriate refresh method.
6. Set the schedule using the supported Tableau Cloud and Bridge configuration.
7. Run a test refresh and check the job status.

Important: Bridge must remain correctly configured and available for scheduled work that depends on it. Supported authentication methods and data connectors vary, so confirm the requirements for your specific source.

Official guide: Keep Data Fresh in Tableau Cloud

12. Authentication and Credentials for Refreshes

A scheduled extract refresh must be able to access the original source without requiring a person to manually sign in each time. Tableau therefore needs an appropriate authentication configuration.

Common Authentication Considerations

• Embedded credentials: Supported database credentials may be stored with the published connection when permitted by the organization's security policy.
• OAuth authorization: Some cloud services use OAuth tokens or connected-account authorization. The required authorization must remain valid.
• Windows or network authentication: Some private data sources require the correct service account, network permissions, or other supported authentication setup.
• File access: Refreshing a file-based source requires the refresh process to access the correct file path and permissions.
• Credential expiration: Expired or revoked credentials can cause scheduled refreshes to fail.

Best Practices for Credentials

• Use approved service accounts for unattended refreshes where appropriate.
• Grant only the database privileges required for the extract.
• Follow the organization's credential-storage and rotation policies.
• Check whether tokens or credentials have expired after a failed refresh.
• Avoid storing passwords directly in scripts, documentation, or shared workbooks.

13. Monitoring Scheduled Extract Refreshes

Creating a schedule is only one part of managing extracts. Administrators and content owners must monitor refresh jobs to ensure they complete successfully and deliver the expected data.

What Should You Monitor?

• Job status: Whether the refresh succeeded, failed, or is still running.
• Start and completion times: Whether the task runs within the expected time window.
• Refresh duration: Whether the job is taking longer than usual.
• Error messages: Whether a connection, authentication, or data-processing problem occurred.
• Data freshness: Whether the dashboard reflects the latest expected source records.
• Resource usage: Whether refresh tasks compete with other important server or database workloads.

Monitoring on Tableau Server

Tableau Server administrators can review refresh activity through the relevant Status and background-task views, including Background Tasks for Extracts where available.

Monitoring on Tableau Cloud

Tableau Cloud users with appropriate privileges can review the relevant job or task interfaces for refresh status, failure details, and scheduling information.

Example Monitoring Table

14. Email Notifications for Failed Refreshes

Failure notifications help data owners and administrators respond when an extract refresh does not complete successfully. Available notification options depend on the deployment and its configuration.

How Notifications Help

• Alert the responsible person to a failed task.
• Reduce the time between failure and investigation.
• Help prevent outdated data from going unnoticed.
• Support operational monitoring for business-critical dashboards.

Recommended Notification Process

1. Identify the owner or team responsible for each important extract.
2. Enable supported failure notifications according to the site's configuration.
3. Make sure notification addresses and ownership details are current.
4. Review failures promptly and record recurring problems.
5. Verify the next successful refresh and the resulting dashboard data.

Do not assume notifications are enabled automatically for every environment. Administrators should verify the relevant settings.

15. Common Extract Refresh Problems and Solutions

16. Best Practices for Scheduling Extract Refreshes

1. Choose a business-appropriate frequency: Refresh as often as needed, not simply as often as possible.
2. Schedule outside peak periods: Avoid competing with critical database workloads where possible.
3. Use incremental refresh strategically: Choose it only when it captures the changes your data requires.
4. Reduce extract size: Remove unused fields and apply appropriate filters before publishing.
5. Test before production: Validate the refresh process and the resulting data before relying on it for business reporting.
6. Monitor failures: Review job history and respond to repeated errors.
7. Secure credentials: Use approved authentication methods and limit access to source data.
8. Document schedules: Record refresh frequency, owner, source, and expected completion time.
9. Avoid unnecessary overlapping work: Stagger task start times where appropriate, especially when source systems have limited capacity.
10. Check the dashboard after important refreshes: A completed job should still be validated against the expected source data when accuracy is critical.
11. Review ownership: Ensure important extracts have a responsible owner or support team.
12. Plan for source changes: Recheck schedules and credentials when database schemas, files, or authentication settings change.

17. Practical Example: Schedule a Daily Sales Extract

Scenario: A retail company uses Tableau to monitor daily sales across multiple branches. The sales database is updated overnight, and managers need the latest data each morning.

Business Requirements

• Refresh the sales extract every day.
• Complete the refresh before managers begin their working day.
• Notify the responsible team when a refresh fails, where supported.
• Verify that new sales records appear in the dashboard.

Implementation Steps

1. Connect Tableau Desktop to the sales database.
2. Select the relevant fields, such as transaction date, branch, product, quantity, and sales amount.
3. Create the dashboard and choose an extract where appropriate.
4. Publish the workbook or published data source to the correct project.
5. Configure the required authentication for scheduled access.
6. Create a daily refresh schedule for a suitable time, such as 6:00 AM.
7. Choose a full or incremental refresh based on the source's update behavior.
8. Run a test refresh.
9. Verify the job status and compare the latest records with the source.
10. Configure monitoring and supported failure notifications.

Expected Workflow

Sales Database Updated Overnight
             |
             v
Daily Refresh Schedule Starts
             |
             v
Tableau Connects to the Source
             |
             v
Extract Refresh Runs
             |
        +----+----+
        |         |
        v         v
     Success    Failure
        |         |
        v         v
Validate Data   Investigate Error
        |         |
        v         v
Dashboard      Fix and Retry
Shows Updated  When Appropriate
Sales Data

Validation Checklist

• Did the refresh job complete successfully?
• Does the extract include the newest expected sales date?
• Do totals agree with the source within the expected reporting rules?
• Are branch and product filters working correctly?
• Can the intended users access the dashboard?

18. Refresh Scheduling and Business Data Freshness

Data freshness describes how recently the information displayed in a dashboard was updated. A refresh schedule helps manage freshness, but the schedule alone does not prove that the data is current.

For example, if a dashboard is scheduled to refresh daily at 6:00 AM but the source database is not updated until 8:00 AM, the 6:00 AM refresh cannot include records that have not yet reached the source.

Factors Affecting Data Freshness

• When the source data is updated.
• When the extract refresh starts.
• How long the refresh takes.
• Whether the refresh completes successfully.
• Whether the source connection uses live data or an extract.
• Whether filters or incremental logic exclude some records.

Best practice: Align the refresh schedule with the source system's update cycle. For important dashboards, define a clear freshness expectation, such as “daily data available by 7:00 AM,” and monitor whether that target is met.

19. Interview Questions and Answers

Q1. What is an extract in Tableau?

Answer: An extract is a stored snapshot or subset of source data that Tableau can use for analysis without querying the original source for every interaction.

Q2. What is extract refresh scheduling?

Answer: It is the configuration of an automated task that updates a published Tableau extract at specified times or intervals.

Q3. Why do we schedule extract refreshes?

Answer: Scheduling reduces manual work, keeps dashboards updated according to business requirements, and helps standardize recurring data updates.

Q4. What is the difference between a full refresh and an incremental refresh?

Answer: A full refresh rebuilds the extract from the source according to its definition. An incremental refresh processes new or qualifying records according to a configured strategy.

Q5. When should an incremental refresh be used?

Answer: It is useful when the source mainly appends new records and a suitable field and supported configuration can identify the records to process.

Q6. What are the risks of incremental refreshes?

Answer: Changes to historical rows, deleted records, and late-arriving data may not be captured as expected. The strategy must be designed and tested carefully.

Q7. Can Tableau Cloud refresh every data source directly?

Answer: No. Direct refresh depends on the source type and connectivity. Tableau Bridge is commonly needed for supported sources that Tableau Cloud cannot directly reach.

Q8. Why can a scheduled refresh fail?

Answer: Common causes include expired credentials, source unavailability, network problems, permission errors, invalid file paths, and resource or timeout limits.

Q9. How can you monitor extract refreshes?

Answer: Use the relevant task or background-job monitoring interfaces to inspect status, duration, errors, and the latest successful refresh.

Q10. What is the role of credentials in refresh scheduling?

Answer: The refresh process must have an approved authentication method and sufficient source-data privileges to access the underlying data without manual intervention.

Q11. Why might a dashboard still show old data after a scheduled refresh?

Answer: The refresh may have failed, may not have run yet, may have refreshed a different asset, or may have run before the source data was updated.

Q12. How can a slow extract refresh be improved?

Answer: Review query performance, reduce unnecessary fields and rows, consider incremental refreshes, and schedule work to avoid competing with other heavy tasks.

Q13. Can refreshes be scheduled during business hours?

Answer: Yes, if the environment and source can support the workload. The schedule should be selected according to data-freshness requirements and resource availability.

Q14. Why should a refresh be tested after scheduling?

Answer: Testing verifies that the connection, credentials, refresh configuration, and resulting data behave as expected before the schedule becomes a critical reporting dependency.

Q15. What is the difference between a live connection and an extract?

Answer: A live connection queries the underlying data source when Tableau needs data, while an extract uses a stored copy that must be updated through a refresh process to reflect source changes.

20. Practice Exercises

1. Create a workbook using a sales dataset and publish it with an extract.
2. Configure a daily refresh schedule and verify the saved settings.
3. Compare full and incremental refresh behavior using a suitable test dataset.
4. Investigate a simulated failed refresh caused by incorrect credentials.
5. Review refresh history and identify the latest successful job.
6. Design a weekly schedule for a report whose source data changes only once per week.
7. Explain when Tableau Bridge is required for Tableau Cloud.
8. Write a checklist for validating the freshness of a daily sales dashboard.

21. Quick Revision Checklist

• Understand what an extract is and why it needs refreshing.
• Know the difference between full and incremental refreshes.
• Understand how refresh scheduling differs between Tableau Server and Tableau Cloud.
• Know when Tableau Bridge may be required.
• Verify that authentication and source connectivity support unattended refreshes.
• Choose a refresh frequency that matches the source update cycle.
• Know where to check refresh-job status and errors.
• Understand common causes of failed or slow refreshes.
• Use filters and remove unnecessary fields when appropriate to reduce extract size.
• Test the refresh and verify the resulting dashboard data.
• Document schedule ownership and monitor critical reports.

22. Conclusion

Scheduling extract refreshes is an important Tableau skill for keeping dashboards and reports updated with source data. By choosing the right refresh frequency, selecting an appropriate full or incremental strategy, configuring authentication, and monitoring task status, developers and administrators can build a more reliable reporting process.

Always remember that a scheduled refresh is an automated attempt to update data, not a guarantee that the dashboard is current. Successful execution and data validation are essential, especially for business-critical reports.

Continue Learning: Explore Tableau Training | Register for a Tableau Course Demo